This phase begins with the onset of a project. Evolving from the feasibility studies for new products, the management's vision or customer need, this phase identifies the product's vision outlining the scope of the project. The charter is drafted, the project community is identified, and the how the team will work together is determined.

Identify and prioritize the features required for creating a product backlog. Spikes may be conducted to validate the concepts prior to providing estimates. High level estimates are gathered in story points or ideal days developing a feature based release plan with milestones and iteration plan to deliver on the vision.

Deliver tested features in short timeframes constantly seeking customer feedback to reduce the risk and uncertainty associated with the project. Gather insights on what worked well, what didn't work well, and what changes are required in retrospective sections. Daily stand-up should be used to gather team's commitment.

Continually monitor the results, review the velocity, and adapt as necessary. The Product Owner focuses on grooming the backlog, the team refactors the code for technical debt, and updates the documents as necessary, and the organization refines the process eliminating delays impeding flow and productivity.

Conclude the project, pass along key learning's and celebrate. In addition to the retrospectives from every iteration, consider a retrospective at the closure of delivering all the features of the project. Subsequently, the administrative closure is followed through as appropriately.